Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect

Summary

RCADA votes ABSTAIN on Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect.

This is a constructive abstention.

RCADA recognises OpenZeppelin as a highly credible organisation in smart-contract security, open-source contract libraries, developer tooling, and ecosystem standards. Cardano would benefit from stronger shared developer building blocks, audited reference patterns, reusable contract components, and clearer paths for external developers and institutions to build safely on Cardano.

However, RCADA is not comfortable voting YES on this proposal as currently structured. The proposal has a valuable strategic objective and a credible proposer, but the current package is broad, expensive, and leaves several important questions open around scope, technical architecture, overlap with existing work, and Treasury value-for-money.

Key Considerations

This is a Treasury Withdrawal governance action.
The requested amount is 11,787,063 ADA.
The proposal is administered by Intersect.
The delivery budget is described as USD $1.831M, calculated at a reference rate of $0.16/ADA.
The proposal includes a 3% Intersect administration fee.
The proposal bundles three main workstreams:
- OpenZeppelin Reference Implementations for Cardano;
- OpenZeppelin Contracts Library for Cardano;
- Security Retainer.
Proposed reference implementations include:
- Cardano Liquid Staking Protocol;
- Self-Repaying Loans Protocol;
- Tokenized Money Market Fund.
The proposal includes developer tooling, documentation, Contracts Wizard integration, AI-enhanced developer tools, co-marketing, and developer enablement.
RCADA supports the goal of stronger open-source developer infrastructure for Cardano.
RCADA is concerned that the proposal is too broad and bundled for a confident YES vote.
RCADA is concerned that key technical decisions, including smart-contract language and toolchain strategy, remain open at the point of funding.
RCADA is concerned about possible overlap with existing or already-funded Cardano developer tooling, standards, and library work.
RCADA would welcome a more focused resubmission with clearer scope, non-duplication analysis, budget detail, and technical architecture.

What this action does

This action withdraws 11,787,063 ADA from the Cardano Treasury to fund the OpenZeppelin Stack for Cardano, administered by Intersect.

The proposal includes three major workstreams:

Workstream	Description
Reference Implementations	Three end-to-end Cardano application blueprints: liquid staking, self-repaying loans, and tokenized money market fund
Contracts Library	A secure, audited, documented contracts library tailored to Cardano’s eUTXO model and Plutus environment
Security Retainer	Security audits, full-stack reviews, penetration testing, continuous coverage, and security reporting for OpenZeppelin-produced code

The proposal also includes:

Contracts Wizard and documentation for Cardano;
OpenZeppelin UI Builder support;
AI-enhanced development tools;
developer tutorials and workshops;
hackathon coaching;
co-marketing and ecosystem adoption activity;
standards contributions, including CIP-113 and a proposed Cardano Contract ABI.

The budget is structured as follows:

Budget item	Amount
Delivery subtotal	11,443,750 ADA
Intersect administration fee	343,313 ADA
Total Treasury withdrawal	11,787,063 ADA

The proposal describes milestone-based payments, with 20% released at legal contract signature and the remaining 80% released across four milestone payments, subject to evidence submission and Intersect Delivery Assurance approval.

Analysis Findings

Constitutional / Guardrails Assessment

✔ The proposal identifies a clear Treasury withdrawal amount.
✔ The proposal identifies the administrator: Intersect.
✔ The proposal provides a 12-month delivery structure.
✔ The proposal includes quarterly milestones.
✔ The proposal includes acceptance criteria and public evidence requirements.
✔ The proposal includes milestone-based disbursement controls.
✔ The proposal uses Intersect administration and treasury-management smart contract tooling.
✔ The proposal includes open-source deliverables.
✔ The proposal includes audit and security review components.
✔ The proposal states that OpenZeppelin has not received Cardano Treasury or Catalyst funding in the prior 24 months.
⚠ The proposal is broad and bundles several major workstreams into one withdrawal.
⚠ The 20% upfront payment is significant given that some important technical decisions remain open.
⚠ The specific smart-contract language targeted is deferred to the initial evaluation phase.
⚠ The proposal would benefit from clearer non-duplication analysis against existing or already-funded Cardano developer tooling and standards work.
⚠ The proposal would benefit from clearer handling of any surplus value if ADA is materially above the reference rate at conversion.

Assessment: Constitutionally structured Treasury withdrawal with meaningful administration controls, but significant scope and value-for-money concerns

Process & Governance Quality

✔ OpenZeppelin is a credible and experienced organisation in smart-contract security and reusable contract libraries.
✔ The proposal addresses a real ecosystem need: stronger shared developer infrastructure and audited building blocks.
✔ The proposal includes milestone-based delivery and public acceptance criteria.
✔ Intersect administration and smart-contract-based treasury management reduce custody and delivery risk.
✔ Published audits and open-source repositories would provide public-good value.
✔ Developer enablement and documentation could improve Cardano onboarding.
⚠ The proposal combines public-good library work with product-specific reference implementations.
⚠ DReps cannot separately approve the contracts library while rejecting or revising the reference implementation scope.
⚠ The proposal’s technical architecture is not settled enough for a foundational contracts-library initiative.
⚠ Cost breakdown is workstream-level rather than sufficiently granular for a proposal of this scale.
⚠ A narrower staged approach would be easier to evaluate and support.

Assessment: Strong proposer and worthwhile objective, but proposal structure is too broad for full support

Impact & Risk Analysis

Potential developer infrastructure value: High
Potential security value: High
Open-source public-good value: Medium to High
Institutional adoption potential: Medium to High
Delivery complexity: High
Scope risk: High
Duplication risk: Medium to High
Technical architecture uncertainty: Medium to High
Budget / value-for-money risk: Medium to High
Administration controls: Medium to Strong
Treasury exposure: Medium

RCADA believes the proposal could create meaningful value if scoped and executed well. However, the current version asks the Treasury to approve a broad package before enough detail is settled around technical direction, overlap with existing work, and budget allocation.

The main concern is not OpenZeppelin’s credibility. The concern is whether this particular proposal is sufficiently focused, specific, and cost-disciplined for a confident YES vote.

Assessment: Constructive ABSTAIN — valuable objective and credible proposer, but proposal is too broad and under-specified as submitted

Ratings (Decision Support Only)

Dimension	Score (1–5)
Constitutional clarity	4
Strategic relevance	4
Proposer credibility	5
Public-good potential	4
Scope control	2
Technical specificity	2
Non-duplication clarity	2
Budget clarity / value-for-money	3
Delivery controls	4
Overall score	🟡 64% — Constructive ABSTAIN due to broad scope, open technical decisions, and value-for-money concerns

RCADA Rationale

RCADA votes ABSTAIN on Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect.

This is a constructive abstention.

RCADA also supports the general direction of improving Cardano’s developer experience. A secure, well-documented, open-source contracts library tailored to Cardano’s eUTXO model could provide real public-good value. Reference implementations, security reviews, documentation, and developer enablement could also help reduce duplicated effort and improve confidence among builders.

However, RCADA is not comfortable voting YES on this proposal as currently structured.

The proposal is large and broad. It combines a Cardano contracts library, three substantial reference implementations, security retainer work, AI-enhanced developer tooling, documentation, co-marketing, standards contributions, and institutional adoption support into one Treasury request of 11,787,063 ADA. While these workstreams may be related, bundling them together makes it difficult for DReps to support the public-good library components without also approving the full scope of product-specific reference implementations and broader enablement work.

RCADA is also concerned that key technical decisions remain open at the point of funding. The proposal states that the specific smart-contract language targeted will be determined during the initial evaluation phase in collaboration with ecosystem stakeholders. For a foundational contracts library, this is a major architectural decision. RCADA would prefer stronger clarity on toolchain, language strategy, interoperability, and how this work avoids fragmentation before approving a large withdrawal.

There is also a non-duplication concern. The proposal’s objectives overlap with areas already being discussed or funded elsewhere in the ecosystem, including developer experience, contract libraries, standards work, CIP-113, and Cardano tooling. RCADA would like to see a clearer gap analysis explaining exactly what is missing, what existing work will be reused, what will not be duplicated, and how OpenZeppelin’s work will integrate with current Cardano-native efforts.

RCADA also has questions around value-for-money and budget structure. The proposal is framed as a USD $1.831M delivery budget calculated at $0.16/ADA, plus a 3% Intersect administration fee. RCADA would prefer clearer handling of any surplus value if ADA is materially above the reference rate at conversion, as well as more granular per-workstream cost detail. The 20% upfront release at contract signature is also significant given that some major technical decisions are still deferred.

RCADA views the Intersect administration structure, milestone-based payments, public acceptance criteria, Sundae Labs treasury-management contracts, and oversight arrangements as meaningful positives. These controls reduce delivery and custody risk, and RCADA appreciates that the proposal includes open-source licensing, public evidence requirements, audits, and milestone verification.

Nevertheless, these safeguards do not fully resolve RCADA’s concerns about scope, sequencing, technical specificity, non-duplication, and Treasury value-for-money. The issue is not whether OpenZeppelin could contribute meaningfully to Cardano. RCADA believes they could. The issue is whether this particular proposal is scoped tightly enough for a confident YES vote.

RCADA would welcome a revised proposal that starts with a narrower and clearer scope, such as an initial Cardano contracts library architecture, gap analysis, toolchain decision, standards alignment plan, and limited pilot implementation. A future version could also separate the core public-good contracts library from product-specific reference implementations, provide more granular budget detail, and clarify ADA/USD conversion surplus handling.

On balance, RCADA abstains because the proposal has a valuable strategic objective and credible proposer, but the current package is too broad and under-specified for full support. RCADA encourages OpenZeppelin and Intersect to continue engaging with the community and return with a more focused proposal that is easier for DReps to evaluate and support.